Update gateways.json #397
Update gateways.json #397
Conversation
Removing ipfs.litnet.work gateway. Can't manage such loads of phishing reports and domain takedown warnings.
|
@itsKV this is a valid frustration and understandable. There has been progress on the blocking front that can be read here: https://blog.ipfs.tech/2023-content-blocking-for-the-ipfs-stack/ There is an alpha implementation available to pull in IPIP-298 which can reduce some headaches, You're always welcome to submit your gateway again if you feel the concerns have been resolved. Thank you for hosting! |
|
This is very optimistic hope for gateway providers. However, a web based and community driven blocking layer can be more manageable. Like AdGuard blocker where blocking service will be hosted at kubo level and denylist will be fetched from publicly managed and audited source (like denylist for AdGuard, but content will be cleartext CID) |
|
🎉 This PR is included in version 1.0.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Removing ipfs.litnet.work gateway. Can't manage such loads of phishing reports and domain takedown warnings.